feat: add support for recurring tasks - #1611

Check if this issue is valid — if so, understand the root cause and fix it. At packages/n8n-node/nodes/Probo/actions/task/update.operation.ts, line 234:

<comment>Updating recurrence always sends the count as a GraphQL string, so values such as `3` fail `Int` input coercion before the mutation runs. Use a numeric n8n parameter (and preserve the empty default for unchanged) to send an integer.</comment>

<file context>
@@ -193,6 +193,54 @@ export const description: INodeProperties[] = [
+	{
+		displayName: 'Recurrence Interval Count',
+		name: 'recurrenceIntervalCount',
+		type: 'string',
+		displayOptions: {
+			show: {
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At pkg/probo/recurring_task_worker.go, line 80:

<comment>A malformed recurrence row can crash or wedge the recurring-task worker: `recurrence_interval_count` is nullable and unconstrained in the migration, while selection only requires a unit. Validate this invariant at the database boundary (and/or skip invalid rows) before dereferencing, since zero or negative counts also make `nextRecurrenceDeadline` loop forever while its transaction remains open.</comment>

<file context>
@@ -0,0 +1,166 @@
+			}
+
+			unit := *task.RecurrenceIntervalUnit
+			count := *task.RecurrenceIntervalCount
+			deadline := nextRecurrenceDeadline(*task.Deadline, unit, count, now)
+
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At apps/console/src/components/tasks/TaskFormDialog.tsx, line 464:

<comment>Opening/rendering this recurrence selector throws because Radix `Select.Item` disallows `value=""`. Use a non-empty sentinel option and map it to null/empty before schema validation and mutation submission.</comment>

<file context>
@@ -393,6 +438,39 @@ export default function TaskFormDialog(props: Props) {
+                      value={field.value ?? ""}
+                      onValueChange={field.onChange}
+                    >
+                      <Option value="">{t("taskFormDialog.recurrenceIntervalUnits.none")}</Option>
+                      <Option value="DAY">{t("taskFormDialog.recurrenceIntervalUnits.day")}</Option>
+                      <Option value="WEEK">{t("taskFormDialog.recurrenceIntervalUnits.week")}</Option>
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At pkg/coredata/task.go, line 51:

<comment>Measure imports now fail at `Task.Upsert`: strict `RowToStructByName[Task]` cannot find either new recurrence field in its `RETURNING` row. Include recurrence columns and args in the upsert insert/conflict clauses and both columns in `RETURNING`.</comment>

<file context>
@@ -37,20 +37,22 @@ import (
+		TimeEstimate            *time.Duration              `db:"time_estimate"`
+		AssignedToID            *gid.GID                    `db:"assigned_to_profile_id"`
+		Deadline                *time.Time                  `db:"deadline"`
+		RecurrenceIntervalUnit  *TaskRecurrenceIntervalUnit `db:"recurrence_interval_unit"`
+		RecurrenceIntervalCount *int                        `db:"recurrence_interval_count"`
+		Rank                    int                         `db:"rank"`
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At apps/console/src/components/tasks/TaskFormDialog.tsx, line 211:

<comment>Non-recurring tasks cannot be submitted with the new defaults: the form starts with count `1` and no recurrence unit, while the new refinement treats that as an invalid count-without-unit combination. Clearing recurrence on an existing task has the same problem because the reset path restores `1`; initializing the count as `null` when no unit is present (or clearing it when the unit becomes `none`) would preserve the intended optional recurrence behavior.</comment>

<file context>
@@ -170,6 +207,8 @@ export default function TaskFormDialog(props: Props) {
         measureId: task?.measure?.id ?? measureId ?? "",
         deadline: task?.deadline?.split("T")[0] ?? "",
+        recurrenceIntervalUnit: task?.recurrenceIntervalUnit ?? "",
+        recurrenceIntervalCount: task?.recurrenceIntervalCount ?? 1,
       },
     });
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At apps/console/src/_locales/fr-FR.json, line 1429:

<comment>The recurringBadge tooltip renders improperly in French for singular counts. `tooltip_one` should use a singular-aware template such as "Se répète chaque {{unit}}" instead of "Se répète tous les {{count}} {{unit}}", which is ungrammatical when count=1 ("tous les 1 jour").</comment>

<file context>
@@ -1413,6 +1424,10 @@
       "delete": "Supprimer"
+    },
+    "recurringBadge": {
+      "tooltip_one": "Se répète tous les {{count}} {{unit}}",
+      "tooltip_other": "Se répète tous les {{count}} {{unit}}"
     }
</file context>

Check if this issue is valid — if so, understand the root cause and fix it. At apps/console/src/_locales/fr-FR.json, line 1430:

<comment>The recurring-task tooltip is grammatically incorrect in French for counts greater than one because both plural branches reuse the singular translated unit (`2 Semaine`, `2 Année`). Providing pluralized unit translations or unit-specific tooltip variants would make the badge readable for all recurrence units.</comment>

<file context>
@@ -1413,6 +1424,10 @@
+    },
+    "recurringBadge": {
+      "tooltip_one": "Se répète tous les {{count}} {{unit}}",
+      "tooltip_other": "Se répète tous les {{count}} {{unit}}"
     }
   },
</file context>